3.2 System health check

MyID provides a web service you can use to perform internal diagnostics and report the result. These diagnostics include performing a number of checks to check the integrity of the installation, then inspecting every method that can be implemented through DCOM to the MyID application server to ensure that the method is available.

3.2.1 Setting up the health check service

By default, the health check service is disabled. To enable the health check service:

1. On the web services server, open the myid.config file in a text editor.

   By default, this file is in the following folder:

   C:\Program Files\Intercede\MyID\SSP\MyIDProcessDriver\

2. In the <MyIDSettings> node, add the following:

   <add key="HealthCheck" value="true"/>

3. Save the file.

Note: You can perform a simple check of the status of the MyID web services server even if you have not enabled the health check service. See the Checking the status of the web services section in the Web Service Architecture guide.

3.2.2 Viewing the report

To view the report, visit the following URL:

<server>/myidprocessdriver/healthcheck.aspx

Where <server> is the address of your MyID web services server. For example:

https://myserver/myidprocessdriver/healthcheck.aspx

By default, the report is displayed in a readable format:

To return the results as machine-readable XML or JSON, append one of the following to the URL:

• ?format=xml

• ?formal=json

For example:

https://myserver/myidprocessdriver/healthcheck.aspx?format=xml

https://myserver/myidprocessdriver/healthcheck.aspx?formal=json

3.2.3 Troubleshooting

3.2.3.1 COM+ errors

Errors in the Object Creation section of the report (marked in red, with the word Failed, and error details such as "Method does not exist") may be caused by:

• Problems communicating with the application server.

• Issues with the MyID COM+ user account – check that the account is valid, and has not changed its password. If you have changed the password, you can use the Password Change Tool to update MyID with the details. See the Password Change Tool guide for details.

• Issues with the COM+ proxies on the MyID web services server. Make sure all the COM proxies have been installed; see the Split deployment section in the Installation and Configuration Guide for details.

• Issues with incorrectly installed COM+ components.

If you have any issues, you can use the System Interrogation Utility to check that your system is configured correctly. See the System Interrogation Utility guide for details.

3.2.3.2 Database errors

If your database is not working correctly, you may see errors similar to the following:

• SQL error 2800 – this may be caused when your server is running, but the MyID database is offline.

• SQL error HYT00 – this may be caused when the database server is not running at all.

If you experience database errors, check that your database is running correctly. To help troubleshoot your issues, you can use the Test Connection option on the Data Link Properties dialog – on the MyID application server, in the Windows System32 folder, double-click the MyID *.udl file that connects to the database that is producing the errors. See your Microsoft documentation for details of any ODBC error codes that appear.